Copyright: © Copyright 1993 Robert Salesas
Citation: © Copyright 1993 Robert Salesas - All Rights Reserved.


EDI Install Pro - User Manual

To obtain help from within an INF Maker dialog box, press F1 when the dialog box is displayed.

•	Important information for owners of previous versions

Basics

•	Introduction

•	Installation procedure

•	Creating a text based INF file

•	Distribution

INF Maker

•	Introduction to INF Maker

•	Using INF Maker

•	INF Maker dialogs

•	Opening and saving INF files

•	Importing and exporting text files

•	INF Maker guidelines

Advanced

•	File compression

•	File splitting

•	Renaming the installer

•	Modiying resources

•	Custom DLLs

Reference

•	Sample INF file

•	INF Sections

Legal information

•	Copyright

•	Disclaimer

•	License agreement

•	License registration

•	Shareware concept

Order information

•	Upgrades

•	Order form

Company information

•	Product line

•	Contact Eschalon Development Inc.


Important information for owners of previous versions

If you own a previous version of EDI Install Pro (1.0 through 1.4), there are some very important additions and changes you should know before proceeding. Do not attempt to use EDI Install Pro 2.x without reading this information.

•	Additions to 2.x

•	Changes to 2.x

Not all new features and changes are listed here, so we recommend you read this new manual very carefully.

Due to these additions and changes, it is important that you do not delete your old version of EDI Install Pro until you have recreated a working INF file with version 2.x.


Additions to 2.x

The most important addition to the EDI Install Pro package is INF Maker. It is a powerful utility that allows you to scan your disks and create an INF file in a matter of minutes. There should be no reason for anyone to create an INF file by hand anymore, but you can still do so if you want to.

The following are some of the new features that have been added:

•	Automatic support for Pen Windows has been added.

•	The packing utilities have been enhanced, as well as new ones added. See the UTILS directory for more details. You may distribute any of the unpacking utilites, but not the packing utilities. Note that UNPACK.EXE is very large and requires Microsoft's CTL3D.DLL library. Due to its size, you might want to distribute WUNPACK.EXE or DUNPACK.EXE. These utilities are not required to be on the distribution disks for EDI Install Pro to function. They are 100% optional.

•	A Version field has been added to the Application section. EDI Install Pro and INF Maker will only work with files of version 2.0.

•	The destination directory dialog has been updated with a directory selection combo box.

•	Disk space size and operating overhead specified for individual files.

•	Required disk space is automatically calculated at run-time, based on selected files.

•	Accurate reporting of percent completed, including for partial installations.

•	User is given the option of closing a file that is currently in use, rather than terminate the installation.

•	Tiled display of a background bitmap.

•	Backup option for file version checking. Files are renamed with the extension .OLD.

•	Component specific creation and modification of INI Items.

•	Optionally running Program Manager if it isn't running.

•	The Program Manager group creation dialog box now lists all available groups in a combo box.

•	Under Windows 3.1, if a Program Manager item already exists, it will be replaced instead of a new one being added. This will not work under Windows 3.0 or some third party shells.

•	Configurable font for the ReadMe window.

•	Resizable or fixed ReadMe window.

•	A log file is now created during the installation. Each file installation, INI item modification, and PM Item creation is logged in INSTALL.LOG on the destination directory.

The log file is appended to, each time the user runs the installer. You or your users can use the log file as a guide for removing the application and restoring the system to its previous state.


Changes to 2.x

The most important change is the fact that the INF file format has changed drastically. In order to create INF Maker, we were forced to drop compatability with previous versions. This is unfortunate, but we believe the advances gained through INF Maker more than make up for it.

We strongly recommend that you do not attempt to convert an old INF file. Using INF Maker, you should be able to recreate even the most complex installations in under an hour. Most installations can be completed in minutes.

The second most important change is the new file format of both compressed and split files. You will have to recompress and resplit all your files using the new versions of PACK.EXE and SPLIT.EXE.

The following are some of the changes that have been made:

•	INSTALL.BIN is now compressed using the standard Microsoft compression utility COMPRESS.EXE which is included with EDI Install Pro. Your installation files are still compressed using PACK.EXE.

•	The INF file encoding method has changed. The utility INFCOMP.EXE has been replaced with INF Maker and INFENCD.EXE. INFENCD.EXE should only be used to encode ASCII text INF files. Files saved with INF Maker are already encoded.

•	The Free Space and Files Total fields have been removed.

•	The Components, Files, and INI Files sections have been drastically changed.

•	The Components entries no longer specify required amount of disk space.

•	The Windows Files and System Files sections have been replaced by fields in each Files entry.

•	The INI Files and PM Group sections have been renamed to INI Items and PM Items.


Introduction

Welcome to EDI Install Pro for Windows!

This manual will guide you through the process of using and understanding EDI Install Pro, and how it can be of benefit to you.

•	What is EDI Install Pro?

•	What does EDI Install Pro do?

•	How does EDI Install Pro work?

Related topics

•	Installation procedure

•	Introduction to INF Maker

•	Creating a text based INF file


What is EDI Install Pro?

EDI Install Pro is a complete installation utility that you can use "right out of the box". It allows your users to easily copy and set up your application on their system. With today's complex applications it is no longer enough to use a batch file to copy your files to their drives. Users demand friendly, easy to use utilities, that provide a simple and precise method of installing applications. This is especially true of Windows, a market so fierce that the first impression can make or break your product.


What does it do?

EDI Install Pro creates the proper directories, copies the files to be installed, creates the Program Manager group items, displays README.TXT files, and more.

The user is always has control over the installation, but doesn't feel burdened by too much information. EDI Install Pro is easy to use by you and your customers, yet allows both of you great leeway in customization.


How does EDI Install Pro work?

EDI Install Pro reads the file INSTALL.INF (refered to as an INF file from now on), which contains the necessary information describing the layout of your files on the distribution disks, as well as a variety of settings and options. To customize your installation process you simply modify the INF file to suit your application.

Unlike some other installers, there are no scripts to write nor new languages to learn. EDI Install Pro uses a simple utility, INF Maker , to create the INF file for you. INF Maker will scan your disks for files and allow you to enter components, INI file entries, Program Manager items, and more. If you prefer, you can create the INF file by hand, using a simple text editor. EDI Install Pro is so complete, and so customizable, that almost anything you need can be easily accomplished.

With EDI Install Pro you won't spend days writing scripts, and your users won't be infuriated trying to set up your product. Trust EDI Install Pro and your installation hassles will disappear.


Installation procedure

EDI Install Pro is extremely easy to use. Your users will be asked a few simple questions and then the installation will begin. They will always have the choice to proceed or cancel the installation, at any point, if they feel uneasy about an operation.

•	User interaction

•	Completing the installation

•	Aborting the installation

Related topics

•	Introduction to INF Maker

•	Creating a text based INF file

•	Modiying resources


User interaction

EDI Install Pro first asks the user for a destination directory, displays the minimum amount of free space required and advises the user if the selected drive doesn't have sufficient space. Optionally, it allows the user to select which components to install.

Throughout the installation EDI Install Pro displays when a file is copied or a Program Manager group is created. This allows the user to feel comfortable with the installation process and not worry about what is being done to their system. The only intervention required is when a new disk needs to be inserted. The user will be prompted for the disks and asked to continue the installation. The user has the option of changing the source path each time EDI Install Pro prompts for a new disk.


Completing the installation

If the installation has been properly completed and the INF file specifies a Program Manager group, the user is asked whether or not it should be created.

Finally, if a README.TXT file was specified, it will be displayed for the user to read. It is a good idea to include last minute, or very important information, that the user must be aware of before using your application.


Aborting the installation

The installation process can be aborted at any time by choosing EXIT INSTALL or CANCEL from any of the dialog boxes. EDI Install Pro will report that the installation was not completed and that the application should not be used in this condition. The files that have been created will have to be manually deleted. This is done as a precaution, since most users would not like the installer to deleting files from their drive.


Creating a text based INF file

EDI Install Pro uses an INF file, typically named INSTALL.INF, to determine what needs to be done. The INF file is actually an encoded version of a file you prepare using either INF Maker  or a plain ASCII editor, such as Windows' Notepad.

We strongly recommend you use INF Maker to prepare your INF files, but if you prefer to do it manually, you may do so.

•	INF File information

•	Preparing the INF file

•	Debugging the INF File

Related topics

•	Introduction to INF Maker

•	Sample INF file

•	INF Sections


INF File information

The INF file is parsed very carefully and you must insure that everything is properly specified. Here are a few things to remember:

1.	You can use as many spaces as you want after the equal sign and they will simply be ignored by EDI Install Pro.

2.	If you use extra spaces before the equal sign, EDI Install Pro will interpret them and won't properly recognize or mis-name the entries.

3.	Any line that starts with a semi-colon is treated as a remark and is ignored by EDI Install Pro. Use it to document your INF file (Note: Comments are stripped out by INF Maker and INFENCD.EXE).

4.	If you don't use Notepad to create your INF file, you should make sure that your editor does not use a CTRL-Z character to terminate the file. EDI Install Pro will read beyond the CTRL-Z and report an error. To make sure you don't have any CTRL-Z characters at the end of your INF file, load it into Notepad and remove any little black squares at the end of the file. The black squares generally look like this: .


Preparing the INF file

If the file is created with an editor, it is typically named  INSTALL.TXT. To encode the text file, you use the INFENCD.EXE utility, which can be found in the UTILS directory. You must only distribute the INSTALL.INF file, not the INSTALL.TXT file. For example, a typical editing session would consist of:

1.	Using Notepad to create the INF file.

2.	Saving the file as INSTALL.TXT to a working directory.

3.	Using INFENCD.EXE to compress the file to the installation disk. It will automatically be named INSTALL.INF.

NOTE:	The unregisted version does not include INFENCD.EXE. It expects INSTALL.INF to be a plain ASCII file. You should create your INSTALL.TXT file and then copy it to the installation disk as INSTALL.INF. Once you register, you will receive INFENCD.EXE. Better yet, use INF Maker  and avoid the hassles.


Debugging the INF File

You must remember that the INF file is like a program's source code. It needs to be tested and debugged under various conditions. We have used and tested the installation program thoroughly, and so far, to the best of our knowledge, there are no major bugs. Still, this only means that the installation program itself is safe, the INF file that you write can still contain bugs. Check that you have properly labeled the disks, that all files have the correct directories and disks, and you have checked that all compressed files are properly marked. If the user attempts to run a compressed file they will be angry when it doesn't work!


Distribution

Below are the general guidelines and rules for distributing your application.

•	Placing files on disk

•	Required distribution files

•	Minimal Readme file

Related topics

•	INF Maker guidelines

•	File compression

•	File splitting

•	Sample INF file

•	INF Sections


Placing files on disk

Files on the distribution disks should be placed in such a way as to minimize disk swapping. Note that an INF file for low density disks will not be the same as one for high density disks. Since the high density disks can hold more files, you won't need as many disks. Keep this in mind when planning the INF file.


Required distribution files

When you have completed the INF file and you have created your distribution disks, you will need to copy INSTALL.EXE, INSTALL.BIN, INSTALL.INF, and optionally UNPACK.EXE, WUNPACK.EXE, or DUNPACK.EXE, to the first disk in your package.

Note that UNPACK.EXE is very large and requires Microsoft's CTL3D.DLL library to function. It might be more appropriate to distribute WUNPACK.EXE or DUNPACK.EXE instead. These utilities are not required to be on the distribution disks for EDI Install Pro to function. They are 100% optional.

The first disk should be clearly identified so the user can locate it easily. You might also consider writing a message similar to this, on the label:

INSERT DISK AND RUN INSTALL FROM WINDOWS.

NOTE:	You may not distribute PACK.EXE, WPACK.EXE, DPACK.EXE, INFENCD.EXE, INFMAKER.EXE or your INSTALL.TXT with your package. Only the files listed above may be distributed. Including other files is a violation of the license agreement.


Minimal Readme file

We suggest you add a README.TXT file to your disk and include something like the following passage, to let customers know about the compressed files:

The executable and library files in this package are compressed. If you don't use the installation program or you need to copy one of the original files onto your hard disk, use the UNPACK.EXE file located in the WinCLI Pro directory or on the diskette.


Introduction to INF Maker

INF Maker is a utility that simplifies the creation of INF files for EDI Install Pro.

EDI Install Pro reads the file INF file which contains the necessary information describing the layout of your files on the distribution disks, as well as a variety of settings and options. To customize your installation process you simply modify the INF file to suit your application.

Unlike some other installers, there are no scripts to write nor new languages to learn. INF Maker takes care of all the details for you. INF Maker will scan your disks for files and allow you to enter components, INI file entries, Program Manager items, and more. If you prefer, you can create the INF file by hand, using a simple text editor.

Related topics

•	Introduction (EDI Install Pro)

•	Using INF Maker

•	INF Maker dialogs

•	INF Maker guidelines


Using INF Maker

INF Maker is very easy to use. All you have to do is fill in the required fields and scan the disks. INF Maker handles all the details for you.

To quickly create an installation script for your application follow these steps:

1.	Layout all the files that belong to your application on the disks. Place them in the correct directory structure you want them to have on the user's system.

2.	Copy INSTALL.EXE and INSTALL.BIN to the first diskette.

3.	Start INF Maker.

4.	Fill in the Application group fields with information pertaining to your application.

5.	Select Dithered from the Background group.

6.	Choose the Scan Disks button.

7.	Choose OK in the Scan Disks dialog.

8.	Enter a name for the first disk (ex: Installation Disk 1).

9.	Type A:\ or B:\ as the path for where your files can be found.

10.	Choose Scan to begin scanning your files.

11.	Repeat steps 8 through 10 for each disk your application requires. Once you have scanned all the disks, choose Done.

12.	You may now save the INF file to your diskette, and run the installation.

You may expand the installation by adding components, modifying the file settings, adding .ini file entries, and creating Program Manager items.

Related topics

•	Introduction to INF Maker

•	INF Maker dialogs

•	INF Maker guidelines


INF Maker dialogs

INF Maker uses a series of dialogs to obtain information on the installation. Except for the Scan Disks dialog, they all use a similiar format.

Dialog	Description

Application 	Main INF Maker dialog. It allows you to enter basic information about your application and the installation.

Disk Labels 	Allows you to change the disk labels for the installation.

Components 	Allows you to create and modify components (sets or groups of files) that the user has the option of installing.

Scan Disks 	Instructs INF Maker to scan the installation disks for files to install.

Files 	Allows you to modify or remove files from the installation.

INI Items 	Allows you to create or modify INI file items to create during the installation

PM Items 	Allows you to create or modify Program Manager items to create during the installation.

Related topics

•	INF Sections


Application dialog

The Application dialog is the main INF Maker dialog. It allows you to enter basic information about your application and the installation.

•	Application actions

•	Application fields

Related topics

•	INF Maker dialogs

•	Application section


Application actions

The following table describes each of the Application action buttons.

Button	Description

Disk Labels 	Allows you to change the disk labels for the installation.

Components 	Allows you to create and modify components (sets or groups of files) that the user has the option of installing.

Scan Disks 	Instructs INF Maker to scan the installation disks for files to install.

Files 	Allows you to modify or remove files from the installation.

INI Items 	Allows you to create or modify INI file items to create during the installation

PM Items 	Allows you to create or modify Program Manager items to create during the installation.


Application fields

The following table describes each of the Application fields.

Field	Description

Name	The name of the application that is to be installed. The name appears in portions of the text and in some dialog boxes.

Title	The title that should appear in the caption of every dialog box. Typically this will be "Application Name - Installation".

Directory	The default directory where you want the application to be installed. The user may change this by specifying a different drive and directory.

PM Group	The name of the Program Manager group to create. This entry is optional and is only required if you want EDI Install Pro to create a group. If you don't want a group created, leave this field blank.

Run PM	Specifies whether or not Program Manager should be run if it isn't loaded when EDI Install Pro tries to create the group.

Background	The type of background to use for the installation. You may set the following options:

NONE	Will not display a background.

DITHERED	Will display the familiar dithered blue background seen in many Windows installations.

BITMAP	Will display a centered bitmap file as specified in the Bitmap File field.

TILED	Will tile a bitmap file as specified in the Bitmap File field. This effect is similiar to Windows' Control Panel option for tiling bitmaps.

Bitmap File	Specifies the bitmap file to use for a background if Dithered, Bitmap or Tiled are specified for the background.

If Dithered is specified for the background, then the bitmap file should be a 2 color (black and white) image to display at the top of the screen. The image is inversed so that the black becomes white and the white becomes invisible.

If Bitmap is specified for the background, then the bitmap file can be any 16 color image. The file should be run-length encoded to save space (Note: Paint Brush does not support RLE files - use Borland's Resource Workshop).

This field is optional.

ReadMe	Specifies a text file to be displayed once the installation has been completed. This file must be copied to the users drive if you wish to have it displayed. The file must be under 16 000 bytes large. This field is optional.

(ReadMe) Font	Specifies the font to use in the ReadMe file viewer. You may select a font from Default, ANSI, System, or OEM. Except for Default, all the fonts are monospaced. If you want to maintain a properly aligned display, select ANSI, System, or OEM. The OEM font will display special IBM characters. This field is optional.

Resizable Window	Specifies a resizable ReadMe file viewer. The user can move and expand the window to view more of the file at a time. Since a resizable window has no DONE button, closing it might be difficult or confusing for novice users. This field is optional.

Custom DLL	Specifies a custom DLL for EDI Install Pro to call. The group consist of two fields - the DLL's file name and whether or not the file is compressed.

If the compressed option is selected, EDI Install Pro will decompress the file as it is copied. Otherwise it will simply copy the file without decompressing it. If the file is compressed, you should specify the name with the appropriate "$" extension (example: INSTLIB.DL$). See the INSTLIB.PAS and INSTLIB.C files for more information. This field is optional.

Debug Mode	This is a special option that sets a debug mode on or off. When this option is set, EDI Install Pro will not copy the files, instead it will just check through the process for errors. This is useful when you have a long INF file to debug and you don't want to wait repeatedly for each file to be copied. Make sure you clear this option before shipping, or your files will not be copied.


Disk Labels dialog

The Disk Labels dialog allows you to manage the labels identifying the installation disks.

When EDI Install Pro cannot find a file on the currently inserted disk, it will prompt the user to insert the appropriate disk. It will use these labels to identify which disk the user should insert.

•	Disk Labels actions

•	Disk Labels fields

Related topics

•	INF Maker dialogs

•	Disks section


Disk Labels actions

To change a disk label, select an item from the list box and modify the label using the Disk Label edit box. Press the ENTER key or choose the CHANGE button to effect the change.

If you wish to cancel an operation, re-select the same item from the list box or select another item. When you are done editing, choose CLOSE.


Disk Labels fields

The disk label should be chosen so that it helps the user recognize which disk to insert. Preferably the label will be printed on the disk in such a way that the user can see it easily. They do not have to be the disks' DOS label.


Components dialog

The Components dialog allows you to manage the components (sets or groups of files) that the user has the option of installing.

You do not need to create any components unless you want the user to be able to do a partial or selective installation. This is very practical with large applications, as the user can choose to install only what he needs.

You can create up to 31 components. If you don't create any components the components button of the main dialog is not displayed during the installation.

•	Components actions

•	Rearranging items

•	Component fields

Related topics

•	INF Maker dialogs

•	Components section


Components actions

To insert a component, select an item from the list box and enter the component name using the Component edit box. Press the ENTER key or choose the INSERT button to insert the component at the current position in the list. To insert a component at the end, select the blank line at the end of the list.

To change a component, select an item from the list box and modify the component name using the Component edit box. Choose the CHANGE button to effect the change.

To delete a component, select an item from the list box and choose the DELETE button.

If you wish to cancel an operation, re-select the same item from the list box or select another item. When you are done editing, choose CLOSE.


Rearranging components

The list box in this dialog supports keyboard and mouse dragging of the selected item. Using the keyboard, select an item from the list box, hold the shift key, and use the cursor keys to move the item up or down the list. Using the mouse, click and hold the mousebutton on the item you want to move, then drag the mouse up or down the list.


Component fields

The component description should be chosen so that it helps the user recognize what that particular component does, and to differentiate it from the other components.

The Total Space Required field is a non-editable, descriptive field stating the total amount of disk space used by the files belonging to this component.


Scan Disks dialog

The Scan Disks dialog allows you to create a list of all the files on your installation diskettes, which you can modify with the Files dialog.

Scanning your diskettes is a two stage process. First you select the scanning method you want INF Maker to use, and then you insert and label each diskette as it is requested.

•	Scan methods

•	Insert and label disks

Related topics

•	INF Maker dialogs

•	Disk Labels dialog

•	Files dialog


Scan methods

The following table describes each of the scan methods:

Scan Method	Description

Update file list and scan for new files	Scans the disks, updating information on current files, and adding new files to the list. For a file to be updated it must reside in the same relative path. The disk is not important. If a listed file is not found on any of the disks, it is deleted from the list.

Delete file list and scan for files	Deletes the current files from the list, and scans the disks adding all files to the list.

Update file list only	Scans the disks updating information on current files. For a file to be updated it must reside in the same relative path. The disk is not important. If a listed file is not found on any of the disks, it is deleted from the list.

You can also set Exclude EDI Install Pro files to have INSTALL.EXE, INSTALL.BIN, INSTALL.INF, the bitmap file, and the custom DLL excluded from the scan.

You may choose OK to start scanning the disks, or CANCEL to abort the operation.


Insert and label disks

Once you start to scan disks, INF Maker will ask you to insert and label each disk successively.

First, type the label in the Disk Label field. If you are rescanning a set of disks, INF Maker will automatically set the old disk label for you. If you prefer a different label, you may select one from the drop down list, or type it in yourself. You must specify a disk label before you can scan a disk.

Next, insert the proper disk in the drive, and type the complete path or select it from the directory drop down list. You may select any directory; you do not have to scan the actual diskettes themselves. For example, you might want to lay out your files on the hard drive as they would appear on your disks. Then when your application is finished, you would create the diskettes. This saves you a lot of time on large installations, since scanning a hard drive is much faster than scanning diskettes.

To begin scanning choose SCAN. When you are finished scanning all the disks, choose DONE. Remember, once you start scanning, you cannot abort the operation. If you selected Update file list and scan for new files or Update file list only as the scanning method, and you choose DONE before all the files have been rescanned, any files in the list that are not found will be deleted.

You are now ready to modify the file settings for your particular needs.


Files dialog

The Files section dialog allows you to manage the files that EDI Install Pro must copy to the user's drive.

•	Files actions

•	Files fields

Related topics

•	INF Maker dialogs

•	Files section


Files actions

To change a file, select an item from the list box and modify the necessary information using the File fields. Choose the CHANGE button to effect the change.

To delete a file, select an item from the list box and choose the DELETE button (Note: This only deletes the entry in the list, not the file on the disk).

If you wish to cancel an operation, re-select the same item from the list box or select another item. When you are done editing, choose CLOSE.


Files fields

The following table describes each of the Files fields.

Field	Description

Description	The description of the file. The description is displayed in the progress dialog box, indicating which file is currently being copied, as well as in the confirmation box for version checking.

File Information	This group contains three fields:

File Path	The complete path of the file. This field is a non-editable, descriptive field only.

Size	The total uncompressed size of the file (in bytes). This field is automatically set by INF Maker everytime you scan the diskettes. There should be no need for you to modify it.

Overhead	The amount of free disk space required by the file for proper operation (in bytes). This amount does not include the file size.

This field is not automatically set by INF Maker, you must individually determine the amount required. For most files, this value will be zero (0).

Component 	The component this file belongs to. The file will only be installed if this component is selected by the user. Choosing «« Always consider file »» ensures that the file will always be considered, regardless of the selected components.

File Type	Specifies the root directory a file belongs in. A file can be of any of the following types:

Application File	This file belongs in the user specified destination directory.

Windows File	This file belongs in the user's WINDOWS directory.

System File	This file belongs in the user's SYSTEM directory.

File Format	Specifies the current format of the file. The file can be any combination of Compressed, Split, or neither. These fields are automatically set by INF Maker everytime you scan the diskettes. There should be no need for you to modify them.

A compressed file will be decompressed during installation. If you attempt to decompress a file that was not compressed using the included utilities, an error will be reported.

A split file will be joined during installation. If you attempt to join a file that was not split using the included utilities, an error will be reported.

A split and compressed file will be joined to a temporary file, and then decompressed to the destination. This will initially require more free space on the users disk. Whenever possible you should place your split files in the first few disks. This allows the space required for the other files to be used as a buffer for the split files.

Version Checking	Specifies a version checking method to use for the file. EDI Install Pro currently uses the file's date to determine if a file is newer. The possible options are:

Always copy	Always copy the source to the destination.

Make backup	If the destination exists, make a backup using .OLD as the extension (example: FILENAME.OLD), and then copy the source to the destination.

Get confirmation	If the destination exists, ask the user to confirm before overwriting with the source.

Copy if newer	Copy the file if the source is newer than the destination.

Newer than system	Search for the file in the users path, WINDOWS directory, SYSTEM directory, and in the destination directory. If the file is found and the source is newer, the file is replaced, wherever it was located.

Because this means that the file might not end up in the directory you specified, it is generally used for system files such as BWCC.DLL or VBRUN100.DLL.

If does not exist	Copy the file if the destination doesn't exist.


INI Items dialog

The INI Items dialog allows you to manage the .INI file items EDI Install Pro creates or modifies on the user's system.

•	INI Items actions

•	Rearranging items

•	INI Item fields

•	Specifying destination directory

•	Deleting .INI files, sections, or keywords

Related topics

•	INF Maker dialogs

•	INI Items section


INI Items actions

To insert an INI item, select an item from the list box and enter the necessary information using the INI Item fields. Press the ENTER key or choose the INSERT button to insert the item at the current position in the list. To insert an item at the end, select the blank line at the end of the list.

To change an INI item, select an item from the list box and modify the necessary information using the INI Item fields. Choose the CHANGE button to effect the change.

To delete an INI item, select an item from the list box and choose the DELETE button.

If you wish to cancel an operation, re-select the same item from the list box or select another item. When you are done editing, choose CLOSE.


Rearranging INI items

The list box in this dialog supports keyboard and mouse dragging of the selected item. Using the keyboard, select an item from the list box, hold the shift key, and use the cursor keys to move the item up or down the list. Using the mouse, click and hold the mousebutton on the item you want to move, then drag the mouse up or down the list.


INI Item fields

The following table describes each of the INI Items fields.

Field	Description

Description	The description of the particular item. The user never sees this description, it is used only to reference the item in the list box.

Component	The component this item belongs to. The item will only be created if this component is selected by the user. Choosing «« Always create item »» ensures that the item will always be created, regardless of the selected components.

.INI File	The .ini file to modify. If the Section, Keyword, and Value fields are empty, the specified file will be deleted.

Section	The section to modify. If the Keyword and Value fields are empty, the specified section will be deleted.

Keyword	The keyword to modify. If the Value field is empty, the specified keyword will be deleted.

Value	The value to assign to the keyword specified above.


Specifying destination directory for an INI item

If you want to specify the destination directory in one of the fields, you must use two consecutive percent signs (%%). EDI Install Pro will replace percent signs with the destination directory, where ever it finds them.

For example, to create a keyword with a value of D:\APPDIR\APP.EXE, where D:\APPDIR is the destination directory, you would specify %%\APP.EXE as the Value. Don't forget the backslash (\) after the percent signs.


Deleting .INI files, sections or keywords

If you leave a field empty, the previous field will be deleted from the .INI file.

For example, to delete the keyword APP EXE from the NEW APP section of the WIN.INI file, you would specify WIN.INI in .INI File, NEW APP in Section, and APP EXE in Keyword. The Value field would be left empty.

If you wanted to delete the whole NEW APP section, you would specify WIN.INI in .INI File, NEW APP in Section, and leave the Keyword and Value fields empty.

Finally, to delete the WIN.INI file itself, you would specify WIN.INI in .INI File and leave the Section, Keyword and Value fields empty.

NOTE:	This is a very poweful feature. You should use it with extreme caution, as deleting entries or files on a user's system is a very dangerous thing to do.


PM Items dialog

The PM Items dialog allows you to manage the Program Manager items that EDI Install Pro creates on the user's system.

If you don't want a Program Manager group, you don't have to create any items. Make sure you leave the PM Group field empty in the Application dialog.

•	PM Items actions

•	Rearranging items

•	PM Item fields

•	Specifying destination directory

•	Specifying relative paths

Related topics

•	INF Maker dialogs

•	PM Items section


PM Items actions

To insert a PM item, select an item from the list box and enter the necessary information using the PM Item fields. Press the ENTER key or choose the INSERT button to insert the item at the current position in the list. To insert an item at the end, select the blank line at the end of the list.

To change a PM item, select an item from the list box and modify the necessary information using the PM Item fields. Choose the CHANGE button to effect the change.

To delete a PM Item, select an item from the list box and choose the DELETE button.

If you wish to cancel an operation, re-select the same item from the list box or select another item. When you are done editing, choose CLOSE.


Rearranging PM items

The list box in this dialog supports keyboard and mouse dragging of the selected item. Using the keyboard, select an item from the list box, hold the shift key, and use the cursor keys to move the item up or down the list. Using the mouse, click and hold the mousebutton on the item you want to move, then drag the mouse up or down the list.


PM Item fields

The following table describes each of the PM Items fields.

Field	Description

Description	The description of the item to create in the specified Program Manager group.

Component 	The component this item belongs to. The item will only be created if this component is selected by the user. Choosing «« Always create item »» ensures that the item will always be created, regardless of the selected components.

Command	The item's associated file and parameters. This command will be executed by Program Manager when the icon is selected.

Icon File	The item's associated icon file. This field signals Program Manager to use an icon in the specified file instead of the program file in the Command field. This field is optional.

Icon Index	The index of the icon to use in the icon file. The index starts at 0, so if you wanted to use the fourth icon in a file, you would specify 3 as the index. This field is optional, and requires the Icon File field if specified.


Specifying destination directory for a PM item

If you want to specify the destination directory in the Command or Icon File fields, you must use two consecutive percent signs (%%). EDI Install Pro will replace percent signs with the destination directory, where ever it finds them.

For example, to add the the destination directory to the Command field and have the icon execute C:\APPDIR\APP.EXE /D=C:\APPDIR, where C:\APPDIR is the destination directory, you would use %%\APP.EXE /D=%%. The same applies for the Icon File field. Don't forget the backslash (\) after the percent signs.

The only time that you won't need to specify the destination directory is if the program can be located on the user's path, WINDOWS directory, or SYSTEM directory.


Specifying relative paths for PM items

The file names should include the destination relative path. For example, to create an item for PROGHELP.EXE located in the PROGRAM sub-directory of the destination directory, you would use %%\PROGRAM\PROGHELP.EXE in the Command field. Don't forget the double percent signs to specify the destination directory.


Opening and saving INF files

EDI Install Pro expects INF files to be saved in a special encoded format produced by INF Maker and INFENCD.EXE. INF files are encoded in order to prevent your customers from tampering with your installation script.

If you have created a text INF file, you will have to convert it before EDI Install Pro can use it. See "Creating a text based INF file" for full details.

Opening an INF file

To open an existing INF file:

1.	From the file menu, choose OPEN.

2.	Type or select the file name.

3.	Choose OK.

Saving to a new INF file

To save to a new (untitled) INF file:

1.	From the file menu, choose OPEN.

2.	Type or select the file name.

3.	Choose OK.

Saving changes to an INF file

To save changes to the current INF file, choose SAVE from the file menu.

NOTE:	The demo version of EDI Install Pro expects INF files to be in ASCII text. Therefore, the demo version of INF Maker does not save files in the encoded INF format, instead all files are saved as plain ASCII text.

Any files you save with the demo version will have to be imported into the registered version, instead of being opened as outlined above.

Related topics

•	Creating a text based INF file

•	Importing and exporting INF files


Importing and exporting INF files

You can import and export INF files that have been saved as plain ASCII text files. This is usually used to handle files you created with an editor such as Notepad. You can use text files to tune an INF file by hand or have one automatically produced with your own programs or batch files. Importing a text file into INF Maker allows you to manipulate it using all of INF Maker's features.

Importing an INF file

To import an INF file:

1.	From the file menu, choose IMPORT.

2.	Type or select the file name.

3.	Choose OK.

Exporting an INF file

To export to a new (untitled) INF file:

1.	From the file menu, choose EXPORT.

2.	Type or select the file name.

3.	Choose OK.

Exported files have a .TXT extension.

Related topics

•	Creating a text based INF file

•	Opening and saving INF files


INF Maker Guidelines

Not available.

Related topics

•	None


File compression

EDI Install Pro supports a reasonable compact and very fast, file compression method. File compression is an integral part of EDI Install Pro, and is therefore very easy to use.

•	Compressing a file

•	Decompressing a file

•	Advantages of compressing files

•	Disadvantages of compressing files

Related topics

•	INF Maker guidelines

•	File splitting

NOTE:	The demo version of EDI Install Pro does not contain the compression and decompression utilities. Only the registered version has the necessary tools to support compression.


Compressing a file

Included with EDI Install Pro is a file compression utility. The Windows utilities PACK.EXE, WPACK.EXE, and their DOS counterpart DPACK.EXE, can be found in the UTILS directory. With them you can compress any of your product's files. When you compress a file, the name is changed by adding one or more dollar signs ($) to the extension. The original name is stored in the file. When you install the application, the real name is extracted and used for the creation of the new file. In the files dialog and section,you must specify the name of the compressed file and not the original name.


Decompressing a file

You or your users may decompress a file with the included redistributable unpacking utilities UNPACK.EXE, WUNPACK.EXE, and DUNPACK.EXE. Since UNPACK.EXE is a Windows application with a simple interface, it is more convenient to use then the command line versions. However WUNPACK.EXE, and DUNPACK.EXE are much smaller, and therefore more attractive when space is limited.


Advantages of compressed files
Advantages of compressing files

Compressed files require less space on the disk and generally take less time to copy, since the CPU usually decompresses faster than the disk drive can transfer the original file. This allows you to use fewer disks, especially if you have a lot of large data files, and decreases the installation time.


Disadvantages of compressing files

Compressing the files saves a lot space and reduces installation time. However this has one big disadvantage - the files may not be manually copied to the drive, as they are useless if not decompressed. Sometimes your users are going to want, or need, to extract only few files, which is why we include the unpacking utilities UNPACK.EXE, WUNPACK.EXE, and DUNPACK.EXE.


File splitting

EDI Install Pro supports file splitting, which allows you to place very large files across mutliple disks.

•	Splitting a file

•	Joining a file

•	Advantages of splitting files

•	Disadvantages of splitting files

Related topics

•	INF Maker guidelines

•	File compression


Splitting a file

To split a large file across multiple disks you must use the SPLIT.EXE utility included in the UTILS directory.

When splitting a file, the name is changed by adding a number to the extension. The original name is stored in the file. When you install the application, the real name is extracted and used for the creation of the new file. You must specify the name of the split file in the files section, and not the original name. INF Maker automatically chooses the proper files for you.

Once you have split the file to the necessary sizes, you must place each file on a separate disk. The disks must be consecutive for EDI Install Pro to properly extract the file.


Joining a file

The only way to join a plit file is to use EDI Install Pro. There is currently utility to manually join a split file. Once the file is split, the installer is the only way to put it together again.


Advantages of splitting files

If you have a file that will not fit on one disk, you don't usually have many options. You can use a larger disk, but that still limits you to 1.44 Mb with a high-density 3½" disk. EDI Install Pro includes a special utilty to split files across multiple disks, thereby removing the limit on file sizes.


Disadvantages of splitting files

Currently, splitting files has one big disadvantage, but only if you compress the file as well as split it. If you compress the file, it will have to be joined to a temporary file before it can be decompressed. This means that the user must have enough free space for the installation, plus for the largest compressed split file. One easy solution to this problem is to install the compressed split file first. This will leave a lot of space available for the temporary file, since most files have not yet been installed.


Renaming the installer

If you prefer to name the installer something else, such as SETUP.EXE, you can do so using the DOS RENAME command or with Windows' File Manager. For example, to change the installer to Setup, you would rename the files INSTALL.EXE and INSTALL.INF, to SETUP.EXE and SETUP.INF. The installer, INSTALL.BIN, stays the same. Remember, you must rename both files, or the installer won't be able to locate the INF file. Also, note that the extensions must remain the same, only the base names can change.


Modifying resources

The main ED Install Pro file, INSTALL.BIN, may be modified using a resource editor, such as Borland's excellent Resource Workshop or Whitewater's Resource Toolkit. With them you'll be able to change any of the strings, the fonts used in the dialogs, and even the dialog layouts themselves. The only thing you are not allowed to change, is the special About dialog box and copyright labels. The About dialog is a "secret" dialog box that only appears if you press ALT-I at the main dialog (it's secret in that the user never gets to see it).

•	Modifying INSTALL.BIN

•	Debugging after modifying INSTALL.BIN


Modifying INSTALL.BIN

To modify INSTALL.BIN, follow the following instructions:

1.	Using EXPAND.EXE (included with Windows), uncompress INSTALL.BIN to a separate temporary directory as INSTALL.EXE. Don't confuse this with the  smaller file of the same name (the "loader"). To not overwrite the loader, you must uncompress INSTALL.EXE to a different directory.

2.	Modify the resources using the resource editor of your choice. We recommend Borland's Resource Workshop or Symantec's Resource ToolKit.

3.	Using COMPRESS.EXE (included with EDI Install Pro), compress the new INSTALL.EXE file as INSTALL.BIN.

4.	Finally replace the old INSTALL.BIN with the new one.

You could use this technique to create French, Spanish, or German installers for your different international markets, or simply to change the look and feel to match your product.


Debugging after modifying INSTALL.BIN

If you are having a problem with the installer not working, please restore the original INSTALL.BIN before you contact us. If the problem still persists with the original file, you may contact us.

NOTE:	When modifying any file, make sure you have a backup of the original. You must never modify the original file, or you won't have anything to revert to if you make a mistake.


Custom DLL

EDI Install Pro supports custom DLLs to expand the available capabilities and to tailor itself to almost any installation's needs. By creating routines to handle special parts of your installation (such as extra setup information or copying specially encoded files), you can completely customize EDI Install Pro without having to write your own installer.

Using DLLs, there's very little that EDI Install Pro can't handle. Custom DLLs expand your possibilities and personalize your installation. Plus, since the DLL can be written in almost any language, you don't have to learn to program in some strange new script language, as with many other installation utilities.

For more information on creating a custom DLL, see the INSTLIB.PAS and INSTLIB.C files. The example files are in Turbo Pascal for Windows and Borland's C++, but a DLL can be written in any language that supports creation of DLLs.


Sample INF file

Below is a sample INF file for EDI Install Pro, generated by INF Maker.

[APPLICATION]

VERSION=2.0

NAME=EDI Install Pro 2

TITLE=EDI Install Pro - Installation

DIRECTORY=c:\windows\install.pro

PM GROUP=EDI Install Pro 2

RUN PM=YES

BACKGROUND=DITHERED

BITMAP FILE=install.bmp

README FILE=readme.txt

README FONT=DEFAULT

RESIZE README=YES

DEBUG MODE=NO

[DISKS]

0=EDI Install Pro - Disk 1

[COMPONENTS]

1=Installer & Utilities

2=Samples and DLL source

3=Documentation

[DIRECTORIES]

1=samples

2=utils

[FILES]

install.txt=install.txt       1639      0 A  2  0   1 N  A

instlib.c=instlib.c          15697      0 A  2  0   1 N  A

instlib.pas=instlib.pas      15845      0 A  2  0   1 N  A

instlib.def=instlib.def        147      0 A  2  0   1 N  A

dpack.exe=dpack.exe           9843   1024 A  1  0   2 N  C

dunpack.exe=dunpack.exe       9175   1024 A  1  0   2 N  C

pack.exe=pack.exe            55296    512 A  1  0   2 N  C

split.exe=split.exe           6297    512 A  1  0   2 N  C

unpack.exe=unpack.exe        54272    512 A  1  0   2 N  C

wpack.exe=wpack.exe          21248    512 A  0  0   2 N  C

wunpack.exe=wunpack.exe      19968    512 A  0  0   2 N  C

infencd.exe=infencd.exe      13248    512 A  0  0   2 N  C

infmaker.exe=infmaker.exe   112896  16384 A  0  0   2 N  C

desc.txt=desc.txt              662      0 A  3  0   0 N  A

readme.txt=readme.txt         1263      0 A  0  0   0 N  N

install.hlp=install.hlp      81518   8192 A  0  0   0 N  C

[INI ITEMS]

Install Directory=0 install.ini "Settings" "Directory" "%%"

[PM ITEMS]

EDI Install Pro=1 "%%\install.exe"

Pack=1 "%%\utils\pack.exe"

UnPack=1 "%%\utils\unpack.exe"

Manual=3 "winhelp.exe %%\install.hlp"

Related topics

•	INF Maker dialogs

•	INF Sections


INF Sections

The INF file is separated into various sections that control different aspects of the installation process. By modifying them you configure EDI Install Pro for your own application.

Section	Description

Application	Contains basic information about your application and the installation.

Disks 	Lists the names of the disks required for the installation.

Components 	Lists the names and sizes of the file components (sets or groups of files) that the user has the option of installing.

Directories 	Lists the names of the directories required for the installation.

Files	Lists all the files that EDI Install Pro must copy to the user's drive.

INI Items 	Lists entries for EDI Install Pro to create or modify in .INI files on the user's system.

PM Items	Describes the Program Manager group that EDI Install Pro will create.

Related topics

•	INF Maker dialogs

•	Sample INF file


Application section

The Application section contains basic information about your application and the installation.

Section contents

An application section must contain at least the following fields: Name, Title, Directory, Free Space, and Files Total. The other fields are optional. A complete section would look like this

[APPLICATION]

VERSION=2.0

NAME=EDI Install Pro 2

TITLE=EDI Install Pro - Installation

DIRECTORY=c:\windows\install.pro

PM GROUP=EDI Install Pro 2

RUN PM=YES

BACKGROUND=DITHERED

BITMAP FILE=install.bmp

README FILE=readme.txt

README FONT=DEFAULT

RESIZE README=YES

INSTALL DLL=instlib.dl$ Y

DEBUG MODE=NO

A minimal section would look like this

[APPLICATION]

VERSION=2.0

NAME=EDI Install Pro 2

TITLE=EDI Install Pro - Installation

DIRECTORY=c:\windows\install.pro

Application entries

The following table describes each of the entries available in the Application section.

Entry	Description

Name	The name of the application that is to be installed. The name appears in portions of the text and in some dialog boxes.

Title	The title that should appear in the caption of every dialog box. Typically this will be "Application Name - Installation".

Directory	The default directory where you want the application to be installed. The user may change this by specifying a different drive and directory.

PM Group	The name of the Program Manager group to create. This entry is optional and is only required if you want EDI Install Pro to create a group. If you don't want a group created, don't include this label or leave it blank.

Run PM	Specifies whether or not Program Manager should be run if it isn't loaded when EDI Install Pro tries to create the group. Specify Yes or No.

Background	The type of background to use for the installation. You may use the following values:

NONE	Will not display a background.

DITHERED	Will display the familiar dithered blue background seen in many Windows installations.

BITMAP	Will display a centered bitmap file as specified in the Bitmap File field.

TILED	Will tile a bitmap file as specified in the Bitmap File field. This effect is similiar to Windows' Control Panel option for tiling bitmaps.

This entry is optional. If you don't specify a value, it will default to Dithered.

Bitmap File	Specifies the bitmap file to use for a background if Dithered, Bitmap or Tiled are specified for the background.

If Dithered is specified for the background, then the bitmap file should be a 2 color (black and white) image to display at the top of the screen. The image is inversed so that the black becomes white and the white becomes invisible.

If Bitmap is specified for the background, then the bitmap file can be any 16 color image. The file should be run-length encoded to save space (Note: Paint Brush does not support RLE files - use Borland's Resource Workshop).

This entry is optional.

ReadMe File	Specifies a text file to be displayed once the installation has been completed. This file must be copied to the users drive if you wish to have it displayed. The file must be under 16 000 bytes large. This entry is optional.

ReadMe Font	Specifies the font to use in the ReadMe file viewer. You may select a font from Default, ANSI, System, or OEM. Except for Default, all the fonts are monospaced. If you want to maintain a properly aligned display, select ANSI, System, or OEM. The OEM font will display special IBM characters. This field is optional.

Resizable ReadMe	Specifies a resizable ReadMe file viewer. The user can move and expand the window to view more of the file at a time. Since a resizable window has no DONE button, closing it might be difficult or confusing for novice users. This entry is optional.

Install DLL	Specifies a custom DLL for EDI Install Pro to call. The entry consist of two fields - the DLL's file name and whether or not the file is compressed. A Y after the DLL path specifices that the DLL is compressed. For example:

INSTALL DLL=instlib.dl$ Y

If the DLL is compressed, EDI Install Pro will decompress the file as it is copied. Otherwise it will simply copy the file without decompressing it. If the file is compressed, you should specify the name with the appropriate "$" extension (example: INSTLIB.DL$). See the INSTLIB.PAS and INSTLIB.C files for more information. This field is optional.

Debug Mode	This is a special option that sets a debug mode on or off. When this value equals Yes, EDI Install Pro will not actually copy the files, instead it will just pretend to do so. This is useful when you have a long INF file to debug and you don't wish to wait uselessly. Make sure you either omit this field or set it to No before shipping, or your files will not be copied.

Related topics

•	INF Maker dialogs

•	Application dialog

•	Sample INF file

•	Components

•	Directories

•	Disks

•	Files

•	INI Items

•	PM Items


Disks section

The Disks section lists the names of the disks required for the installation.

When EDI Install Pro cannot find a file on the currently inserted disk, it will prompt the user to insert the appropriate disk. It will use these labels to identify which disk the user should insert.

Disks entries

Each entry consists of an integer number (1 to 32000); an equal sign; and the name of the distribution disk. For example,

[Disks]

1=WinCLI Pro Disk #1

2=WinCLI Pro Disk #2

Disk numbers

The numbers are only used internally and need not be consecutive, although it makes more sense to do so (for example: 1, 2, 3, 4, 5; rather than: 1, 45, 33, 56, 78).

Disk labels

The disk label should be chosen so that it helps the user recognize which disk to insert. Preferably the name will be printed on the disk in such a way that the user can see it easily. They do not have to be the disks' DOS label.

Related topics

•	INF Maker dialogs

•	Disk labels dialog

•	Sample INF file

•	Application

•	Components

•	Directories

•	Files

•	INI Items

•	PM Items


Components section

The Components section lists the names of the components (sets or groups of files) that the user has the option of installing.

You do not need to include this section unless you want the user to be able to do a partial or selective installation. This is very practical with large applications, as the user can choose to install only what he needs.

If this section is omitted from the INF file, the components button of the main dialog  is not displayed during the installation.

Components entries

Each entry consists of an integer number (1 to 31), an equal sign, and the description of the component. For example,

[Components]

1=Applications & Utilities

2=Documentation & Help

3=Extras

You can have up to a maximum of 31 components per INF file.

Component numbers

You'll want to use 1 to 31 for your component numbers. Number zero (0) is reserved and specifies that an entry should always be copied or created, regardless of what components the user selects.

Component description

The component description should be chosen so that it helps the user recognize what that particular component does, and to differentiate it from the other components.

Related topics

•	INF Maker dialogs

•	Components dialog

•	Sample INF file

•	Application

•	Directories

•	Disks

•	Files

•	INI Items

•	PM Items


Directories section

The Directories section lists the names of the directories required for the installation. EDI Install Pro will attempt to create the directories as required by the installation.

EDI Install Pro uses this section to determine which directory on the distribution diskette contains the file and to which directory, relative to the destination, the file is to be copied. The path is always relative to the source and destination, which the user specified.

Only directories that are required for a file to be installed, will be created. To force EDI Install Pro to create an empty directory, place a "dummy" file in it (Note: You can use the file deletion feature of INI Items to remove the dummy file).

Directories entries

Each entry consists of a number (1 to 32000); an equal sign; and the name of the directory. For example,

[Directories]

1=Utility

2=Samples

3=Samples\Pascal

4=Samples\C

Directory numbers

The numbers are only used internally and need not be consecutive, although it makes more sense to do so (for example: 1, 2, 3, 4, 5; rather than: 1, 45, 33, 56, 78). Number zero (0) is reserved and specifies the root directory. You can use zero (0) in the files section whenever you need to specify the destination directory itself. For example,

install.hlp=install.hl$	81518	8192	A	3	1	0	C	A

↑ Directory

would place the INSTALL.TXT file in the user specified destination directory.

Related topics

•	INF Maker dialogs

•	Sample INF file

•	Application

•	Components

•	Disks

•	Files

•	INI Items

•	PM Items


Files section

The Files section lists all the files that EDI Install Pro must copy to the user's drive.

Files entries

Each entry consists of a description, an equal sign, and 9 information fields. The description is displayed in the progress dialog box, indicating which file is currently being copied. It may contain spaces, commas, quotes, and other special characters, except an equal sign.

Entry fields

The 9 fields in a Files section entry are: File name, File Size, File Overhead, File Type, Component, Disk, Directory, Format, and Version Checking. All the fields are required and must appear in the order described below.

install.hlp=install.hl$	81518	8192	A	3	1	0	C	A

↑ File Name	↑ File Size	↑ File Overhead

↑ File Type

↑ Component

↑ Disk

↑ Directory

↑ Format

↑ Version Checking

The following table describes each of the fields in a Files section entry.

Field	Description

File Name	The exact name of the file to be copied, as it appears on the disk. Do not specify the path. If the file is compressed, you should specify the name with the appropriate "$" extension (example: FILENAME.EX$). EDI Install Pro will automatically create the destination file with the original name.

File Size	The total uncompressed size of the file (in bytes). It is important that this field matches the real file size. If it doesn't, the check for the amount of disk space required and the meter bar updating won't function properly. INF Maker simplifies the task of checking file sizes by automatically scanning all the files.

File Overhead	The amount of free disk space required by the file for proper operation (in bytes). This amount does not include the file size. For most files, this value will be zero (0)..

File Type	Specifies the root directory a file belongs in. A file can be of any of the following types:

A	Application file. This file belongs in the user specified destination directory.

W	Windows file. This file belongs in the user's WINDOWS directory.

S	System file. This file belongs in the user's SYSTEM directory.

Component 	The component number that this file belongs to. A file will only be copied if the component was selected by the user. If you don't include a Components section, you can specify zero (0) as the component number. An entry with zero (0) as the component will always be copied, regardless of what components the user selects.

Disk 	The disk number that contains the file to be copied. EDI Install Pro first attempts to read the file in the current disk and if the file cannot be located, it prompts the user to insert the specified disk.

Directory 	The directory number that contains the file to be copied. The source path is constructed by combining the source directory, this directory, and the file name. The same process is used to construct the destination path.

Format	Specifies the current format of the file. The following formats are supported:

C	File is compressed and should be decompressed during installation. If you attempt to decompress a file that was not compressed using the included utilities, an error will be reported.

N	Copy the file normally, without decompressing it. No error is reported if a compressed file is copied without being decompressed.

S	The file is split and should be joined during installation. If you attempt to join a file that was not split using the included utilities, an error will be reported.

SC	The file is split and compressed, and should be joined and decompressed during installation. A split and compressed file will first be joined to a temporary file, and then decompressed to the destination. This will require more free space on the users disk.

To split a large file across multiple disks you must use the SPLIT.EXE utility included in the UTILS directory. Once you have split the file to the necessary sizes, you must place each file on a separate disk. The disks must be numbered consecutively. You specify the first disk in the series with the Disks field above. Remember to include an entry in the Disks section for each disk the split files require.

Version Checking	Specifies a version checking method to use for the file. EDI Install Pro uses the date to determine if a file is newer. The possible options are:

A	Always copy the source to the destination.

B	If the destination exists, make a backup using .OLD as the extension (example: FILENAME.OLD), and then copy the source to the destination.

C	If the destination exists, ask the user to confirm before overwriting with the source.

N	Copy the file if the source is newer than the destination.

S	Search for the file in the users path, WINDOWS directory, SYSTEM directory, and in the destination directory. If the file is found and the source is newer, the file is replaced, wherever it was located.

Because this means that the file might not end up in the directory you specified, it is generally used for system files such as BWCC.DLL or VBRUN100.DLL.

X	Copy the file if the destination doesn't exist.

Related topics

•	INF Maker dialogs

•	File dialog

•	Sample INF file

•	Application

•	Components

•	Directories

•	Disks

•	INI Items

•	PM Items


INI Items section

The INI Items section lists entries for EDI Install Pro to create or modify in .INI files on the user's system. This section is optional.

INI Items entries

Each entry consists of a description; an equal sign; the component this entry belongs to; the .INI file to create or modify; the section name; the keyword; and the value to assign to the keyword. For example, to create the following section in WIN.INI,

[WinCLI]

Color=Black

you would use

App INI=0 WIN.INI WinCLI Color Black

Using spaces in keys or values

Any time that you wish to use a space or a tab for anything other than separating fields, you should enclose the field in quotation marks. For example,

App INI=1 WIN.INI NewApp "App Exe"

Specifying destination directory

If you want to specify the destination directory in one of the fields, you must use two consecutive percent signs (%%). EDI Install Pro will replace percent signs with the destination directory, where ever it finds them. For example, to create the following section in WIN.INI,

[NewApp]

App Dir=D:\APPDIR

App Exe=D:\APPDIR\APP.EXE

you would use

[INI Items]

App INI=1 WIN.INI NewApp "App Dir" %%

App INI=2 WIN.INI NewApp "App Exe" %%\APP.EXE

Deleting .INI files, sections, or keywords

If you leave out the section name, the keyword, or the value, the specified part will be deleted from the .INI file. For example, to delete the App Exe item of the NewApp section listed above, you would use:

[INI Items]

App INI=2 WIN.INI NewApp "App Exe"

If you wanted to delete the whole New App section, you would use

[INI Items]

App INI=3 WIN.INI NewApp

Finally, if you wanted to delete the .INI file itself, you would use

[INI Items]

App INI=4 WIN.INI

NOTE:	This is a very poweful feature. You should use it with extreme caution, as deleting entries or files on a user's system is a very dangerous thing to do.

Related topics

•	INF Maker dialogs

•	INI Items dialog

•	Sample INF file

•	Application

•	Components

•	Directories

•	Disks

•	Files

•	PM Items


PM Items section

The PM Items section describes the Program Manager group that you want EDI Install Pro to create.

If you don't want a Program Manager group, you don't have to include it. If you exclude this section, you should also exclude the PM Group entry of the Application section.

PM Items entries

Each entry consists of the name of the item to create; an equal sign; the component this entry belongs to; the file's path name and parameters (enclosed in quotation marks if necessary); the icon file's path name; and the icon index. Only the component and the file name are required, the icon file name and the icon index are optional. A complete entry would look like this

WinCLI=1 WINCLI.EXE WINCLI.EXE 0

A minimal entry would look like this

WinCLI=1 WINCLI.EXE

Specifying destination directory

Most of the time you will want to specify the destination directory as the file's path, so that Program Manager is able to locate the file. You must use two consecutive percent signs (%%) to specify the destination directory. EDI Install Pro will replace the percent signs with the destination directory in the program and icon file specifications. For example,

EDI Install Pro=1 %%\INSTALL.EXE %%\INSTALL.EXE

ReadMe=2 "NOTEPAD.EXE %%\README.TXT" NOTEPAD.EXE

would tell EDI Install Pro to add the destination directory to the program and icon file names when creating the Program Manager item. Don't forget the backslash (\) after the percent signs.

The only time that you won't need to specify the destination directory is if the program can be located on the user's path, WINDOWS directory, or SYSTEM directory.

Specifying parameters

If you wish to specify any parameters along with the file's path name, you must enclose the command line (program name and parameters) in quotation marks. For example,

ReadMe=2 "NOTEPAD.EXE %%\README.TXT" NOTEPAD.EXE

WCLICtrl=3 "WCLICTRL.EXE /C /N /S"

Any time that you wish to use a space or a tab for anything other than separating fields, you should enclose the field in quotation marks.

Specifying icon files

By specifying a different icon file, Program Manager will use an icon in the specified file instead of the program file. The icon index is used to determine which icon (0..?) will be used from the icon file. For example,

WinCLI Pro=1 WINCLI.EXE WINCLI.EXE 3

would tell Program Manager to us the 4rth icon (0, 1, 2, 3 = 4rth icon) in WINCLI.EXE.

Specifying relative paths

The file names should include the destination relative path. For example, to create an item for PROGHELP.EXE located in the PROGRAM sub-directory of the destination directory, you would use PROGRAM\PROGHELP.EXE as the path name.

[PM Items]

Program Help=1 %%\PROGRAM\PROGHELP.EXE

When specifying relative paths, it is usually necessary to specify the destination directory as well, using the double percent signs.

Related topics

•	INF Maker dialogs

•	PM Items dialog

•	Sample INF file

•	Application

•	Components

•	Directories

•	Disks

•	Files

•	INI Items


Copyright

© Copyright 1993 Robert Salesas. All Rights Reserved. This software product is protect by by Canadian and United States laws, international copyright treaties and all other applicable national laws. This software product and documentation may not, in whole or part, be copied, photocopied, translated, or reduced to any electronic medium or machine readable form, without prior consent in writing, from Robert Salesas and according to all applicable laws.

Related topics

•	Disclaimer

•	License agreement

•	License registration

•	Shareware concept


Disclaimer

This information is provided "as is" without representation or warranty of any kind, either express or implied, including without limitation, any representations or endorsements regarding the use of, the results of, or performance of the information, its appropriateness, accuracy, reliability, or correctness. The entire risk as to the use of this information is assumed by the user. In no event will Robert Salesas or Eschalon Development Inc. be liable for any damages, direct, indirect, incidental or consequential, resulting from any defect in the information, even if Robert Salesas or Eschalon Development Inc. have been advised of the possibility of such damages. This disclaimer shall supersede any verbal or written statement to the contrary. If you do not understand or accept these terms you must cease and desist using this product immediately.

Related topics

•	Copyright

•	License agreement

•	License registration

•	Shareware concept


License agreement

The use of this package indicates your understanding and acceptance of the following terms and conditions. If you do not understand or accept these terms, or your local regulations prohibit "after sale" license agreements, you must cease and desist using this product immediately.

1. Copyright: These programs and the related documentation are copyright and protected by Canadian and United States laws, international copyright treaties and all other applicable national laws. The sole owner is Robert Salesas.

2. Operating License: You may not use, copy, modify, or transfer the programs, documentation, or any copy except as expressly defined in this agreement. You have the non-exclusive right to use any enclosed program only on a single computer at a time. You may load the program into your computers temporary memory (RAM). You may physically transfer the program from one computer to another, provided that the program is used on only one computer at a time. You may not decompile, disassemble, reverse engineer, modify, or translate the program or the documentation. You may not attempt to unlock or bypass any copy protection utilized with the program. You may not remove or modify any copyright notice nor the About dialog box or the method by which to invoke it.

3. Distribution License: You may distribute the EDI Install Pro run-time files (INSTALL.EXE, INSTALL.BIN, UNPACK.EXE, WUNPACK.EXE, and DUNPACK.EXE) as long as their intended and possible use is only to install an application, other than themselves, on a users computer. No other files or documents from the EDI Install Pro package may be distributed. You may not distribute copies of the complete package or the accompanying utilities and documentation.

4. Back-up and Transfer: You may make one (1) copy of the program solely for back-up purposes. You must reproduce and include the copyright notice on the back-up copy. You may transfer the product to another party only if the other party agrees to the terms and conditions of this agreement and completes and returns a registration card to Eschalon Development Inc. If you transfer the program you must at the same time transfer the documentation and back-up copy or transfer the documentation and destroy the back-up copy.

5. Terms: This license is effective until terminated. You may terminate it by destroying the program, the documentation and copies thereof. This license will also terminate if you fail to comply with any terms or conditions of this agreement. You agree upon such termination to destroy all copies of the program and of the documentation.

6. Other rights and restrictions:  All other rights and restrictions not specifically granted in this license are reserved by Robert Salesas and/or Eschalon Development Inc.

Related topics

•	Copyright

•	Disclaimer

•	License registration

•	Shareware concept


License registration

If you choose to use EDI Install Pro you must own a license. You are not allowed to keep, use, or distribute EDI Install Pro with your applications unless you obtain a license. Doing so is a violation of our copyright and is punishable by Canadian and United States law, as well international copyright treaties.

When you register for a license, we will send you the latest version of the package. It will not have the opening delay screen that you get with the demo version, plus it will support compression. You will also receive utilities to pack, unpack, and split your files.

Related topics

•	Copyright

•	Disclaimer

•	License agreement

•	Shareware concept

•	Upgrades

•	Order form

•	Product line

•	Contact information


Shareware concept

Shareware is copyrighted software which is distributed by authors through bulletin boards, on-line services, disk vendors, and copies passed among friends. It is commercial software that you are allowed to try before you pay for it. This makes shareware the ultimate in money back guarantees!

Most money back guarantees work like this: you pay for the product and then have some period of time to try it out and see whether or not you like it. If you don't like it or find that it doesn't do that you need, you return it and you get your money back. Some software companies won't even let you try their product, since to qualify for a refund the diskette envelope must have an unbroken seal.

With shareware you get to try it for a reasonable limited time (like 30 days), without spending a penny. You are able to use the software on your own system, in your own special work environment, with no sales people looking over your shoulder. If you decide not to continue using it, you throw it away and forget all about it. You only pay for it if you continue to use it.

Shareware is a distribution method, not a type of software. You benefit because you get to use the software to determine whether it meets your needs, before you pay for it. Authors benefit because they are able to get their products into your hands without the expenses it takes to launch a traditional retail software product. There are many programs on the market today that would never have become available without the shareware marketing method.

The shareware system and the continued availability of quality shareware products depend on your willingness to register and pay for the shareware you use. It's the registration fees you pay which allow us to support and continue to develop our products. Please show your support for shareware by registering those programs you actually use and by passing them on to others. Shareware is kept alive by your support!

Related topics

•	Copyright

•	Disclaimer

•	License agreement

•	License registration


Upgrades

We periodically provide bug fixes and upgrades for our products.

Upgrade policy

Minor changes and bug fixes are free; major revisions carry an upgrade fee. If we release a new version within 15 days of your purchase, and it is similiarly priced, we will provide the upgrade free of charge. Shipping and handling is always extra.

Upgrading to EDI Install Pro 2.0

If you already own a copy of EDI Install Pro versions 1.0 through 1.4, you may upgrade to EDI Install Pro 2.0 or to the EDI Install Pro 2.0 Developer Package for a discounted price. See the order form for details. Make sure you order under the same name and address as the original product, or advise us of the changes.

Related topics

•	Order form

•	Contact information


Order form

Click mouse button here to print an order form.

For information, orders, or site licenses, call or fax Eschalon Development Inc. at (604) 520-1543, or send an EMail message on Compuserve at 76625,1320. Due to the large size of the product, we are no longer able to ship electronically (such as through CompuServe).

NAME/CONTACT:

COMPANY:

STREET:

CITY:	STATE:	ZIP:

COUNTRY:	TELEPHONE:	FAX:

EDI Install Pro 2.0	$125.00 Cdn.	($99.95 US)	x ___ units =	$ ________

Upgrade from 1.0 - 1.2	$63.00 Cdn.	($49.95 US)	x ___ units =	$ ________

Upgrade from 1.4	$32.00 Cdn.	($24.95 US)	x ___ units =	$ ________

Developer Package 2.0	$189.00 Cdn.	($149.95 US)	x ___ units =	$ ________

Upgrade from 1.0 - 1.2	$94.00 Cdn.	($74.95 US)	x ___ units =	$ ________

Upgrade from 1.4	$63.00 Cdn.	($49.95 US)	x ___ units =	$ ________

Sub-Total:	$ ________

Canada shipping and handling (Air Mail $5 Cdn., Rush $10 Cdn.)	$ ________

United States shipping and handling (Air Mail $5 US, Rush $20 US)	$ ________

Overseas shipping and handling (Air Mail $10 US, Rush $40+ US)	$ ________

(For overseas rush orders, please contact us before ordering.)

Sub-Total:	$ ________

B.C. residents add 6% PST	$ ________

Canada residents add 7% GST	$ ________

Total:	$ ________

[  ] VISA*	[  ] US/CDN Check	[  ] US$ Bank Draft	[  ] P.O. (with our approval)**

(*We cannot accept MasterCard or Amex at this time. **Please do not send P.O.s without contacting us first!)

P.O./	Issued on/

VISA #:*	Expiration Date:

(*Your order will be charged in Canadian dollars.)

Approved by/

Name on Card:	Signature:

NOTE:	Orders can take up to 48 hours to get processed. Please consider this when you place a rush order. Also note that due to the large increase of rush orders, everything is taking longer to process. We ask that you not wait for the last minute to place your order. We can't offer special treatment to any particular order.


Product line

Eschalon Development Inc. product line as of March 1st, 1993.

Product	Price (US $)

EDI Install Pro for Windows 	$99.95

EDI UnInstall for Windows 	$99.95

EDI Install for MS-DOS 	$45

EDI Threads for Windows	$99.95

EDI Power Libs for Windows 	$99.95

WinCLI/WinCLI Pro 	$35/$79.95

LZSSLib, Single/Distribution 	$25/$299.95

All of our products can be ordered directly through us. You can download the "demo" versions from CompuServe (WINSDK or WINADV sections, usually).


EDI Install Pro for Windows - Version 1.4
EDI Install Pro for Windows - Version 2.0

EDI Install Pro is a powerful, full-featured installation utility. Most everything you need is included, in a simple to use format - no programming is required. However, if you need to add a specialized feature, you can do so with your own custom DLLs.

Your customers will feel right at home with its standard, professional interface. We don't clutter our windows with useless gadgets or hokey graphics. In our opinion, a clean, standard interface, makes for a better product, and leaves a lasting impression.

EDI Install Pro does not waste your time forcing you to learn yet another script language. It uses a simple INF file format that makes creating powerful installations a breeze. In fact, using the included INF Maker utility you can complete most installations in minutes!

 Unlike some of our competitors, we don't charge royalties, and we don't require you purchase a license for each product you distribute. After all, you don't purchase a new compiler for every program you develop!

Call and order EDI Install Pro today and your first impression will always be a good one! Features:

•	High-quality,  standard interface.

•	Powerful INF Maker utility simplifies creation of installation.

•	Dithered, tiled or bitmap backgrounds.

•	Progress bar keeps user informed.

•	Selectable components allow users to perform partial installations.

•	.INI creation and modification.

•	Creates Program Manager groups.

•	Built-in readme file viewer.

•	Efficient file compression/splitting.

•	Multiple version checking options.

•	Extensive error checking.

•	Small size is perfect for single disk.

•	Supports multiple disks - all sizes.

•	Fully expandable via custom DLLs.

•	No royalties and no hidden costs.

•	Plus much, much more!

You can do almost anything you need with EDI Install Pro, just as it is. However, by allowing custom DLLs, you can expand the capabilities to include anything you need, such as custom setup information, custom component selection, advertising text, file encryption, autoexec.bat or config.sys modifications, and much more. We couldn't include every possible feature, but with a custom DLL you can add anything you need.


EDI UnInstall for Windows - Version 1.0

Finally, a utility that allows users to uninstall your applications! Using a simple INF File, EDI UnInstall deletes application files, removes Program Manager groups, removes or changes .INI files or sections, and optionally deletes user data files. It will leave no trace of the previously installed application! EDI UnInstall uses the same attractive interface and simple file format as EDI Install Pro. Users and reviewers alike, are now demanding the option to uninstall. Can you risk not using EDI UnInstall?


EDI Install for MS-DOS - Version 1.0

EDI Install for MS-DOS is a complete implementation of our famous Windows installer written specifically for MS-DOS. Features a pleasant text based windowed interface which gives your users a good first impression of your product. This versions uses the same INF file format introduced in EDI Install for Windows, making it just as easy to learn!


EDI Threads for Windows - Version 1.0

EDI Threads is a complete multi-threading library for Windows. With it you can easily create applications that use background printing, complex redrawing, repagination, serial port polling, text searches, and more. There is no need to wait for Windows NT or switch to OS/2. With EDI Threads, writing background processes for Windows applications becomes a snap. Here are just some of the features you'll find:

•	Easy to use, even when converting existing applications.

•	Almost any function can be turned into a thread.

•	Speeds up application's response time.

•	Automatic system-wide scheduler.

•	Unlimited number of threads.

•	Each thread uses it's own stack.

•	Adjustable priorities and time slices.

•	Pause or stop a thread at any time.

•	There is practically no limit to what a thread can do, including Windows and DOS calls.

•	NO ROYALTIES.

The threads operate independently of the main program. As soon as a thread is started, control is returned to the application. By applying this technique to a background operation you will drastically speed up the application's user response time. Instead of waiting for a task to finish, you can start it and return to the user without delay. No more coffee breaks during lengthy operations!

NOTE:	Pascal/assembler source is now available for $395 US ($465 Cdn).


EDI Power Libs for Windows

EDI Power Libs provides a complete set of powerful routines to simplify your programming tasks. Use EDI Power Libs instead of re-inventing the wheel every time you need a new feature. It will save time and money, while providing greater flexibility.  Here are just some of the features you'll find:

•	Low-level functions: fast data manipulation, inline memory access, process yielding, DOS wrapper calls, easy DPMI access, debugging aids.

•	High-level functions: sound, friendly delays, timing (count-down, "dead-man", difference, etc.), string manipulation (conversions, editing & handling, parsing, DOS functions, etc.), date & time (international, calculations, conversion), pattern matching (file and buffers).

•	DOS functions: copy, move, rename, enumeration, share checking, file locking, drive type, disk labels, safety and error checking, string parsing, etc.

•	Fast inline macros for system critical requirements.

•	Full on-line documentation and examples.

•	Dynamically linked library format included for languages with DLL support (i.e. Pascal, C, C++, Visual Basic, and more)*.

•	Source code included (Pascal and Assembly).

•	Plus much, much more!

*Only some language interface modules are included; check with us regarding availability.

NOTE:	EDI Power Libs for Windows should be available in June 1993.


WinCLI/WinCLI Pro* - Version 3.0/1.0

WinCLI Pro is a complete command line interface capable of running Windows applications as well as DOS applications. It replaces the usual DOS prompt on standard and enhanced mode systems. Also included over 30 built-in file management commands (ALIAS, ASSOCIATE, ATTRIB, CD, CLS, COPY, DATE, DEL, DIR, EXIT, FINDFILE, HELP, INFO, LABEL, MEM, MAKEDIR, MORE, MOVE, PATH, PROMPT, RENAME, RENDIR, RMDIR, SYSINFO, TIME, TITLE, VER, VERIFY, VOL, WHICH and many other extended commands).

WinCLI Pro has full clipboard support, a detailed help system, command line editing, command line history, aliases (like Doskey macros in MS-DOS 5.0), a scroll-back buffer, selectable font and adjustable colors. Also included in the package is a complete File Manager replacement, settings utility, password system protector, clock & screen saver and various other small utilities.

*Some features are only available in WinCLI Pro.


LZSSLib - Version 1.0, Single/Unlimited license

Complete compression/decompression DLL for Windows. Quickly and easily add compression support to your current applications. Supports Turbo Pascal for Windows, C/C++, Actor, Visual Basic, Object Vision 2.0 and any language product that supports DLLs*.

*Only C and Pascal interface code is included.


Contact Eschalon Development Inc.

For technical assistance, orders, site licenses, upgrades or information on our other products, you may contact us at:

Address:	Eschalon Development Inc.

110-2 Renaissance Square

New Westminster, BC

V3M 6K3   Canada

Telephone/Fax:	(604) 520-1543

BBS Support:	Planned for May 1993

CompuServe:	76625,1320

Internet:	robert_salesas@mindlink.bc.ca